docker: fix script check execution #24098
Merged
+3
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #24095 we made a fix for non-streaming exec into Docker tasks for script checks and
change_mode = "script"
, but didn't complete E2E testing. We need to useContainerExecAttach
in the new API in order to get stdout/stderr from tasklets, but the previousContainerExecStart
call will prevent this from running successfully with an error that the exec has already run.Note for reviewers: at this point the
(*taskHandle).Exec
and(*driver).ExecTaskStreaming
are similar enough that I suspect we could at least partially merge them, but I'm trying to avoid adding more churn to this code during the beta window. I'd also like to fix this more universally for other driver authors when we tackle NET-11219E2E run of the currently-failing tests: